Nailing the Interview

You've built strong stories using the High-Signal Storytelling (HSS) framework from Chapter 3. You've matched them to the level you're targeting. Now comes the critical moment: the interview itself.

You're not going to perform a rehearsed monologue at the interview. You'll be having a genuine dialogue with your interviewers, and you will need to present to them your capable, authentic, professional self.

It is possible to sabotage months of preparation with an hour of poor delivery. Many candidates recite memorized scripts that sound robotic. They panic if they’re interrupted. And they miss the signals from the interviewers about what matters most to them.

This chapter will teach you to deliver your stories smoothly while maintaining the structure that makes them powerful. You'll learn how to be fully present in the conversation, handle whatever comes your way, and communicate effectively under pressure.

This chapter covers three phases: before, during, and after the interview.

Before the Interview

The work you do before stepping into an interview determines how well you'll perform during it. This preparation is more than putting together stories and memorizing them. You also need to prepare your mind and body, think about logistics, and plan to arrive with time to spare.

Preparing Your Mind and Body

Your brain needs the right conditions to perform well in high-stakes conversations. Technical interviews demand quick thinking, clear communication, and sustained focus. You can't achieve this with poor sleep and three cups of coffee.

The Night Before

Aim for seven to eight hours of sleep. Your ability to think clearly, recall details, and adapt to unexpected questions degrades significantly if you’ve had insufficient sleep. (If poor sleep is a chronic issue for you, consider addressing your sleep quality in the weeks and months leading into interviews as a core aspect of your preparation.) The night before your interview, wind down earlier than usual. Avoid looking at any screen for an hour before you go to bed. Consider meditation to calm your mind. If you know you won't hit the full seven to eight hours, don't stress about it. Do the best you can, and focus on the other aspects of your preparation that you can control.

Set up everything the night before to avoid unnecessary stress in the morning. Lay out what you are going to wear. Test your technology, if it’s a video interview. If it’s in person, plan your route. There is a detailed checklist later in this chapter (see Final Logistics and Setup).

These small preparations will free your mind to focus on the conversation itself.

The Day Of

Stick to your normal eating routine. If you're a breakfast eater, include protein and complex carbohydrates to maintain your energy through the interview. If you typically skip breakfast and function well without it, don't force yourself to eat just because it's interview day. Your goal is to avoid a dramatic change to your routine.

Time your caffeine intake and hydration carefully. You want to be alert but not jittery. If you normally drink coffee, have your normal amount at your normal time. Interview day isn't the time to experiment with triple espressos or energy drinks. Drink water steadily throughout the morning, but not so much that it makes you want to use the bathroom all the time.

Light physical activity helps many people think more clearly. Take a short walk before your interview. Do some gentle stretches. The purpose is to get your body and mind connected. Movement helps dissipate nervous energy and improves focus.

Being Present

The difference between good and great interviews often comes down to presence. When you're fully engaged in the conversation, you can more easily pick up on what matters to the interviewers. You find it easier to adapt your stories to their interests, and you’re able to think more clearly about your answers to follow-up questions.

Presence starts with breathing. When we're nervous, we breathe shallowly, from our chest. This reduces the quantity of oxygen flowing to the brain, which can amplify any anxiety we may have. Before the interview, take five deep belly breaths. During the interview, use transitions between questions to take a deep breath. This simple practice will help to keep you grounded.

Listen with your whole attention. When the interviewer asks a question, resist the urge to immediately start formulating your answer. When they finish, take a beat to make sure you have understood what they're asking. This pause may feel long to you, but it suggests to them that you’re being thoughtful. Better to take three seconds to process the question and prepare your answer than to misinterpret the question or answer the wrong one entirely.

Be curious about the interviewers and the role. If you know the names of your interviewers beforehand, review their LinkedIn profiles or any public information about their work. This helps you to ask them informed questions and find points of connection with them. Real curiosity about their work comes through naturally. Good questions make for better conversations because you're not trying to pass a test; you're figuring out whether this role fits your career goals. Even if you leave the interview knowing that the role and the company would not be a good fit for you, you can consider it to have been a successful interview for that reason.

Making a Strong First Impression

People form judgments within seconds of meeting you. That might seem unfair, but first impressions shape how interviewers hear everything that follows. A strong first impression is a good starting point, and it will create a positive lens through which they evaluate your stories. Give a weak first impression, and you’ll be working uphill to change their initial assessment.

Your intent should not be to manipulate or deceive. You want to show up as your genuine professional self in a way that helps the interviewers see you in a positive light from the start.

Three elements help to influence and build upon first impressions in interviews: appearing sharp, being enthusiastic, and projecting a sense of expertise.

Sharp: Preparation and Presence

"Sharp" means you look well put together and well prepared. You’re well-groomed and wearing the appropriate attire. For video interviews, this means the lighting is good, and there is a clean background. You’ve checked that the audio quality is good, and the camera has been set at your eye level. For in-person interviews, arrive before time (but not excessively early), bring relevant materials with you, and project confidence.

Just as important, you need to be mentally present from the first moment. Make eye contact when you greet the interviewer. Offer them a firm handshake (if it’s an in-person interview). Sit up straight, because that signals you're ready to engage. These small signals communicate that you will be taking this conversation seriously.

Enthusiastic: Energy and Engagement

By projecting enthusiasm, you are signaling that you want to be there and are actually interested in the role. This doesn't mean forced cheerfulness or over-the-top excitement. Approach the conversation with positive energy and show the interviewer that you are interested in what they have to say.

Your tone of voice matters more than you might think. Speaking in a monotone will suggest that you are disengaged. On the other hand, if you speak in a varied tone with the right level of intensity, you’ll show that you're present and engaged. Watch for uptalk (i.e., your sentences ending with rising inflection, as if asking a question), as this can suggest uncertainty. Make your statements sound like statements.

Don't sit on your hands or fold your arms in front of you. Place your hands on your lap or on the table, and be ready to use them. Using gestures to explain concepts will change your vocal energy and make you seem more lively and less scripted. Smile naturally at appropriate times. Signal active listening by leaning in slightly when the interviewer speaks, and repeat what they say to you in your own words if you need to buy time to think. These subtle behaviors will make the conversation more engaging for both of you.

Be enthusiastic when talking about your work, the way you would with a friend who's in the same field. If you're proud of a project, that'll come through. Authentic enthusiasm about your work is contagious, and it will give your stories more impact.

Expert: Confidence and Competence

"Expert" doesn't mean you know everything or never admit to any uncertainty. It means you communicate with the confidence that comes from competence. You've got the experience, you understand your domain, and with the help of this book, you can explain complex topics clearly. This expertise should be evident in how you carry yourself and structure your responses.

Expertise shows up in specific ways: you give real details instead of generalities, you explain the trade-offs behind your decisions, you're honest about what you don't know, and you connect ideas across different experiences.

Avoid undermining your expertise with excessive hedging. It is far better to say, "We reduced latency by 40%" instead of "I think we may have improved performance by around 40% or so." State your contributions clearly without minimizing or exaggerating them. Let your work speak for itself through your clear, confident communication.

The Opening Thirty Seconds

At the beginning of your conversation with an interviewer, you will set the tone for everything that follows by how you project those three elements in the opening greeting, your brief introduction, and your engagement with their first question.

When the interviewer greets you, listen actively and remember their name. When they ask you to introduce yourself, deliver a crisp, well-structured response (see Chapter 4, The Essential Questions). And when they ask their first question, pause briefly to show you're thinking, then deliver a clear response. Used well, these opening moments will establish you as someone who is sharp, enthusiastic, and expert.

The Right Mindset

Most candidates treat the interview like a performance where every word matters. This mindset creates anxiety and makes you self-conscious. There's a better way to think about it.

Conversation, Not Performance

A behavioral interview is a conversation between professionals about work experiences, and that’s how you should treat it. You're not performing a one-person show. You're discussing your experience with someone who understands your field. They're not judging you like a critic reviews a play. Rather, they're trying to understand how you think and work and how you might be able to contribute to their company.

This distinction is important, because conversation has different rules. When candidates treat interviews like scripted performances, they focus on not messing up. Small mistakes in your speech get magnified in your mind. But conversations are fluid. Authenticity matters more than polish. Interruptions are just a part of natural engagement rather than disruptions.

Once you accept that interviews are conversations and that everyone stumbles over words sometimes, you can relax. You'll listen better, and you'll adjust your stories to what the interviewer actually cares about. You'll ask questions when something's unclear. It stops being a performance and starts being a real conversation.

Exploring Mutual Fit

You're not just trying to impress them, because you're also figuring out whether you'd actually want this job. Taking a role that's wrong for you wastes everyone's time.

Yes, they're evaluating you. But you're also evaluating them, and having this mindset will reduce any anxiety you might have by equalizing the power dynamic. Their questions will tell you what they value, and their responses to your questions will reveal their priorities and culture. Just as your interviewers are doing, you're gathering information to make an informed decision. If they offer me this role, would it be right for me, and should I accept it?

This shift is visible. You ask better questions when you actually want to know the answers. You're more relaxed when you're not desperate for approval. And you will make better decisions about which offers to accept. Companies respect candidates who show thoughtful evaluation of fit.

Transforming Anxiety into Curiosity

Interview anxiety usually comes from one place: worrying about being judged. Curiosity pulls you in the opposite direction because instead of thinking about how you're being evaluated, you're thinking about the role, the team, and the problems they're working on. You can feel both at once, but leaning into the curiosity will serve you much better.

Before each interview, think of something specific that you want to learn about the role or the company. Maybe you're curious about their technical architecture, or you want to understand how they approach a specific type of problem. Perhaps you're interested in their team dynamics or growth opportunities. Be curious throughout the interview.

During the interview, if you feel anxiety rising within you, shift your attention back to curiosity. What is this interviewer telling you about the key requirements for the role? What can you learn from their questions? What interesting challenges does their team face? This redirection will keep you present and engaged, whereas feeding your anxiety could send you spiraling into self-judgment.

The Preparation Hierarchy

Preparing well for an interview entails preparing the right things in the right way. You want to go in there with a structure in your mind that is ready to use, not a memorized script on your tongue.

What to Memorize

There are some things you will need to memorize. Three elements per story, but let the exact words vary each time:

The Headline: Know your opening sentence cold. This will ground you, and starting with a headline will confirm to the interviewer right from the start that you have understood the question. Practice it enough that you can deliver it smoothly while making eye contact. But even here, small variations from the memorized headline will help to keep it conversational. Sometimes you might say, "Last year, when I was working on..." and, other times, "My best example of that was when..." or "I helped our team to..." That way, the words will feel fresh to you and the interviewer, while the core message stays consistent.

Your Key Points: Remember the behavioral moments that form the backbone of your story. Think of these as waypoints on a journey. You know you need to hit them, but the path between them can vary based on the conversation. If you have three key points about investigating a bug, designing a solution, and implementing it, those waypoints stay fixed. But the way you describe each one can be adapted to the interviewer's interest level and follow-up questions.

The Landing: Know your numbers and what you took away from the experience. These are what make the story stick. Practice describing the impact of your work in different ways. For example, "We reduced errors by 90%" or "Customer complaints about this issue essentially disappeared." Working this sort of flexibility into your landing helps you to emphasize what matters most to each interviewer.

Everything else should flow from the conversation. The supporting details, technical explanations, and context should all emerge organically. If you've practiced enough, these details will come without having to be forced.

Finding Your Natural Language

Corporate speak kills authenticity, and it makes you sound like everyone else. Compare these versions:

Corporate speak: "I leveraged cross-functional stakeholder alignment to drive operational excellence initiatives that yielded substantial productivity gains."

Natural language: "I got three teams to agree on a new process that saved everyone about five hours a week."

The second version is clearer, more credible, and it’s easier to deliver naturally. It also invites follow-up questions because the interviewer knows what you actually did.

Speaking plainly takes practice, because we absorb corporate jargon from job descriptions, meetings, and company decks without realizing it. You have to actively strip it out. As you practice, think about how you would explain technical concepts to friends or family. That is the language you want to use in interviews.

Technical precision is important, but it shouldn't come at the cost of clarity. You can be accurate without being difficult to comprehend. For example, "We made the app load twice as fast by storing frequently used data in memory" is both precise and clear.

Practice Conversing

Traditional methods of practicing for interviews, for example, recording yourself delivering word-for-word monologues, create the wrong sort of muscle memory because it trains you to perform rather than converse. Therefore, it should never be your only mode of practice. Instead, try these approaches that build real conversational skills in an interview setting:

Story Interruption Drills: Have a practice partner interrupt you randomly with clarifying questions. Mid-sentence, they might ask, "Wait, how many people were on the team?" or "What made you choose that approach?" Learn to pause, answer them clearly, and then smoothly continue with your narrative. Practicing this will build comfort with the natural flow of a technical conversation, because engaged interviewers are likely to interrupt you with questions.

Key Point Shuffle: Practice telling your stories with the key points in different orders. For example, instead of explaining the problem, then your investigation, then the solution you applied, try starting with the solution and working backwards. Or lead with the most interesting technical challenge. Developing this level of flexibility will enable you to show that you understand the content deeply, and you will easily be able to adapt your story to what interests the interviewer most. It will also prevent you from getting thrown off if an interviewer asks you to skip ahead or go back.

Conversational Paraphrasing: Start by confirming you understand what the interviewer is really asking for, then adapt your story to emphasize the most relevant aspects. Next, practice telling the same story three times using completely different words each time. Building a repertoire of ways to express the same ideas will help to break any reliance you might have on a script. For example, you might describe a performance issue as being "painfully slow," or "taking 30 seconds when it should have taken 3," or that it "made users think the app had frozen." Different ways of phrasing the problem will suit different contexts. If you can vary your language freely in response to the situation, you won’t sound rehearsed.

Your goal is to be so comfortable with your material that you can deliver it naturally without thinking too hard. When you know your stories this well, you can focus on the conversation instead of trying to remember what comes next.

Truthfulness is Non-Negotiable

Everything in this book assumes you're telling true stories about real experiences. This is not negotiable. Even small lies or exaggerations in behavioral interviews are dangerous, and they are likely to be exposed.

Behavioral interviews employ deep-dive questioning. When you share a story, the interviewers will probe specific details: your exact role, the team dynamics, the technical decisions you made, the obstacles you faced, and the outcomes you achieved. If you've fabricated or significantly embellished any part of your story, your answers to these questions will likely expose inconsistencies. You might remember the broad strokes of a fabricated story, but you are not likely to be able to think of (and memorize) detailed made-up answers to all the possible questions that you could be asked.

Interviewers who have conducted a large number of behavioral interviews will have strongly developed instincts for lies. They will notice when a candidate’s answers become vague under pressure. They will catch contradictions between the different parts of a story. They will recognize the difference between genuine recall and fabricated detail. Once they suspect dishonesty, they will probe harder, and the interview will essentially end there.

Beyond the practical risk of getting caught, dishonesty undermines the entire purpose of behavioral interviews. Companies use them to understand how you think and work. If they want to hire you, they want to hire the real you, not a fictional character that you've created. If your stories can't show the capabilities they’re looking for, the role may not be the right fit for you.

If you lack the perfect story for a specific question, use the strategies set out in the section "Handling the Unexpected" that comes later in this chapter. You can adapt related stories, explain what your hypothetical approach would be, or reach back to earlier experiences. All of these options will maintain your integrity while still providing value to the interviewer. There's never a good reason to lie.

Progressive Practice

Build your interview skills by practicing deliberately at progressively increasing levels of difficulty. Move to the next milestone only when you feel comfortable at the current one, not based on any fixed schedule. Some people may need a week between milestones, others a month. Proceed at your own pace.

Milestone 1: Solo Recording – Record yourself telling stories to build a baseline comfort with hearing your own voice. Don't worry about being perfect; just get used to telling your stories out loud. This builds self-awareness about your pacing, clarity, and verbal tics. Watch these recordings and take notes on how you can improve.

Milestone 2: Practice with Non-Technical Friends – Practice with friends or family, and get them to ask you basic follow-up questions. Answering their naive questions from outside your field will help you eliminate jargon and provide clear explanations. If your friend doesn't understand why something was challenging, you need to use simpler language. Working on this milestone will build your ability to explain complex work to diverse audiences. This is an important skill to work on because not all interviewers will be deep technical experts.

Milestone 3: Mock Interviews with Professionals – Carry out mock interviews with tech professionals who understand your domain. They can probe your technical decisions realistically and ask the kinds of follow-up questions you'll likely face in real interviews. This will give you practice defending your decisions under scrutiny and help you build technical depth in your storytelling.

Milestone 4: Lower-Stakes Real Interviews – If possible, schedule your first interviews with companies you're less excited about but from which you would still consider accepting an offer. Real stakes change the dynamic entirely, and these experiences will teach you what to expect. The pressure of a real interview can't be fully simulated. You will learn to manage your nerves, maintain your presence under pressure, and recover from any mistakes you make.

Each milestone targets a different skill. Recording builds self-awareness. Friends force you to drop jargon. Mock interviews sharpen your technical depth. And nothing replaces the real thing.

Final Logistics and Setup

The logistics matter more than you'd think. Getting the small stuff right means you can focus on the conversation.

Your Pre-Interview Checklist

Create a checklist and run through it both the night before and 30 minutes before the interview (or before you leave the house for it).

The Night Before:
For all interviews:

• Prepare what you’re going to wear, and sort out the materials you’ll bring with you, including copies of your resume, your story bullet points, and your portfolio.
• Review the profiles of your interviewer(s) if you know their name(s).
• Check the backup contact information for the interviewer.

For video interviews:

• Test the video platform, camera, microphone, and internet connection.
• Set up your interview space with a clean desk, good lighting, and minimal distractions.

For in-person interviews:

• Plan your route, parking, and timing.
• Confirm building access instructions if needed.

Getting There (In-Person Interviews):

• Before you leave, review the role description and your research notes on the company.
• Leave early enough to give yourself a buffer for unexpected delays.
• Find a quiet spot nearby to take five deep breaths and center yourself before entering the building.
• Arrive at the building 15 minutes early, and check in 5 minutes before the interview time.

30 Minutes Before (Video Interviews):

• Review the role description and your research notes on the company.
• Close all applications that could generate notifications.
• Do a final tech check on camera angle, lighting, and audio.
• Place water within reach.
• Take five deep breaths to center yourself.
• Join the meeting 2-3 minutes early.
• For coding interviews, make sure your laptop is charged and your IDE is open.

Video Interview Setup

Camera Position: Place your camera at eye level. Looking down at a laptop camera creates psychological distance and makes you appear less engaged. Prop your laptop on books or use an external webcam to achieve the ideal camera position. Ensure your face is centered and your eyes are on the top third of the frame. Look at the camera when speaking, not at the interviewer's face on your screen. This will feel unnatural at first, but if you are looking at the screen, it will make you appear to be looking down. Practice this before interview day, so it becomes more comfortable.

Background: Keep it simple and professional. A blank wall or neutral bookshelf works well. A messy room is distracting. Virtual backgrounds can often glitch and distract from your message. However, if you must use one, test it thoroughly with different lighting conditions and movements. Some interviewers like seeing a bit of personality in your background. Others prefer neutral. If you're not sure, keep it clean and simple.

Audio Quality: Use headphones with a good microphone. Poor audio makes it harder for interviewers to understand you, and it will exhaust them. Built-in laptop microphones pick up room echo and background noise. Even basic earbuds with a microphone will dramatically improve audio quality. For the best audio quality, use a separate microphone. Test your setup with a friend to ensure you sound clear.

Lighting: Face a window or place a lamp in front of you to ensure there is even light on your face. Backlighting could turn you into a silhouette. Side lighting will create dramatic shadows. If you are interviewing at night, point a simple desk lamp at the wall behind your monitor to create a soft, flattering light.

Notification Management: Close all browser tabs and applications from which you could receive notifications. This includes email, Slack, Discord, WhatsApp, text messages, and any social media. Put your phone on Do Not Disturb mode. An unexpected notification sound or pop-up could distract both you and the interviewer and disrupt your flow.

Note Placement: Put bullet points for your story headlines near your camera or on paper notes on your desk. This lets you glance at reminders. But don't read from notes. Your bullet points are a safety net, not a script. Be aware that companies are increasingly alert to candidates who appear to be reading from AI tools or getting outside help during interviews. If an interviewer asks, be upfront that you have a few bullet points with your story headlines and show them your papers, as handwritten notes are acceptable. Transparency about brief personal notes is far better than appearing evasive or looking like you're using AI assistance.

Hydration: Keep a water bottle within reach in case your mouth gets dry. Taking a small sip during a natural pause is perfectly acceptable.

Technical Backup: Have your phone ready as a hotspot in case the internet connection fails. Test this backup connection before the interview. Keep the interviewer's contact information accessible on a different device. If the video fails completely, being able to quickly switch to the phone will show your professionalism under pressure.

Technical Readiness: If the interview involves coding or technical demonstrations, ensure your laptop is fully charged and plugged in if you’re using one. Have your preferred IDE or development environment already open. Test that you can share your screen if needed. Don't wait until the interview starts to discover your battery is at 5% or your coding environment needs updates.

In-Person Interview Preparation

Arrival: Arrive 15 minutes early, but don't announce yourself until 5 minutes before. Use the extra time to find the bathroom, check your appearance, and take a few calming breaths. Walking in flustered from rushing will undermine your presence.

What to Bring: Carry a portfolio with copies of your resume and a page of bullet points for your stories. Include a pen and paper for notes. Even if you never reference these materials, having them near reduces any anxiety. Bring breath mints and tissues. (Small comforts matter when you're nervous.)

Managing Wait Time: Long waits in reception areas can drain your energy. Stay off your phone except for quick time checks. Instead, review your story headlines mentally. Observe the office environment for conversation starters. Stay alert with good posture and occasional movement.

During the Interview

With the preparation work done, you can now engage in the conversation. Your task during the interview is to be present, responsive, and real, while ensuring your key messages come through clearly.

Create Real Conversations

The best behavioral interviews feel like engaging technical discussions. Your role is to keep this conversation moving while ensuring your key messages come through.

Why Interruptions Signal Engagement

Many candidates panic when interviewers interrupt their stories, but this reaction misses the point, because only engaged interviewers will ask you questions. They're not judging your story to be inadequate. Rather, they want to explore the areas that interest them or connect to the challenges their teams face.

When you are interrupted, resist the urge to rush through your answer and then race back to resuming your story. The interruption is the conversation. Give the question your full attention, and answer it thoroughly. Then ask if they want more detail on that specific point before continuing your story.

Here's how to handle interruptions smoothly:

1. Pause immediately and make eye contact.
2. Answer their specific question completely.
3. Confirm with them that you've answered their question to their satisfaction (e.g., "Does that answer your question?" or "Did that address what you were asking about?").
4. If no, ask them to clarify exactly what they were after, and give your answer accordingly.
5. If yes, check if they want more detail ("Should I elaborate on that?").
6. Bridge back to your story: "So, after solving the database issue, I..."

This keeps the conversation flowing. The interviewer gets their question answered, and you still hit your key points.

Sometimes interruptions reveal the things that really matter for this role. For example, if they dig deep into how you handled stakeholder communication during your technical project, that likely signals that the role will involve significant cross-functional work. Therefore, take the cue and adapt your remaining stories to emphasize collaboration.

Follow the Interviewer's Lead

Your story might be about performance optimization, but if the interviewer keeps asking about team dynamics, follow their interest. They're telling you what matters for this role and what they’re curious about.

This doesn't mean you have to abandon your structure. Hit your key points, but lean into whatever they're most interested in. If they keep asking about how you got people on board, spend more time on that. If they probe the technical design, go deeper there.

Active following looks like this:

Note their questions: Pay attention to patterns in their follow-up questions, because that will tell you what matters most for the role. For example, if they ask two questions about testing, they probably value quality engineering. Respond by weaving testing considerations into your next story. You should pull details from your prepared base layer up into your behavioral core preemptively when you recognize what matters to the interviewer.

Build on their comments: If they say, “We've struggled with that, too,” you can briefly ask about their experience. But keep it short; you still need to hit your key points, and going off track is the biggest risk here. Don't let it derail you. Keep it brief, and stay aware of the time.

Match their energy: Some interviewers want rapid-fire exchanges. Others prefer thoughtful, detailed discussions. If you can, try to mirror them and match their pace. However, this can be challenging to pull off during an actual interview while also managing your stories, so don't force it if it feels unnatural.

The Power of Check-Ins

Allay any anxiety that you may have about whether or not you're on track with simple check-ins. These are brief questions to keep the conversation collaborative:

• "Should I go into more technical detail on the dynamic caching strategy?"
• "Would it be helpful to explain the team dynamics first?"
• "I can share more about the rollout process if that's useful."

Check-ins serve multiple purposes. They show respect for the interviewer's time. They prevent you from overexplaining topics they don't care about. They create natural breakpoints in your stories. Best of all, they convert monologues into dialogues.

Use check-ins strategically. After explaining a complex technical concept, check understanding. Before diving into implementation details, check interest. When you see the interviewer taking notes, pause and check to see if they need clarification. Chapter 3 introduced check-ins when preparing your base layer for follow-up questions. Later in this chapter, "The Pyramid Method for Follow-Ups" shows how to structure check-ins between levels of detail.

But don't overdo it. Checking in after every sentence will make you appear uncertain. Use them at natural transition points between major sections of your story.

Handling the Unexpected

Despite thorough preparation, you should still expect to field unexpected questions. Having a response strategy will keep you confident when this happens. You have four main options, and you can choose whichever fits the situation best.

Option 1: The Related Story

Your first option is to adapt a story from a related competency. Consider a situation where you have been asked about conflict with your manager, but you had only prepared a story covering conflict with team members. You might say something like this:

"I haven't had a situation with true conflict with my manager, but I can share a time when my team and I strongly disagreed on a technical approach. The discussion got pretty heated because we all cared deeply about the decision..."

An answer like this shows self-awareness while still showing relevant skills. You have acknowledged the slight mismatch but are still able to provide value. Most interviewers will appreciate the honesty and will either accept the related story or adjust what they're looking for.

When using related stories, explicitly connect them to the original question. Explain why you think the example you’re providing shows related skills. Forcing an unrelated story never works, because interviewers can tell. If you can clearly explain why your example shows the same skills they're looking for, most interviewers will accept it.

Option 2: The Hypothetical Approach

If you truly lack relevant experience that can be connected to their question, share how you would approach the situation your interviewer has asked about. An approach like the following will show your judgment even in the absence of a perfect example:

"I haven't faced that specific scenario, but based on similar challenges, I would start by understanding my manager's underlying concerns. In my experience with technical disagreements, I've found that apparent conflicts can often come from a mismatch in priorities. I'd probably set up a one-on-one conversation first to understand their perspective..."

This works best when you have some related experience to draw from. You're not inventing a story because you're walking the interviewer through how you'd actually handle it based on what you've done before. Be specific about the steps. “I would communicate clearly” tells the interviewer nothing. But “I would document the trade-offs in a shared doc and ask each person to rank their priorities”‌ shows real thinking.

Option 3: Distant Examples

Sometimes you need to reach beyond your recent professional experience. It is important to frame these examples appropriately:

"This takes me back to college when I led our robotics team. We had an intense disagreement about our competition strategy. While it's not recent professional experience, the way I handled it shows how I approach conflict. Half the team wanted to focus on speed, while the other half wanted precision. The debate got personal because we'd all invested months into the project..."

Or you could refer to volunteer work that you’ve done:

"I haven't dealt with this at work, but I ran into something close when I organized a hackathon. The organizing committee couldn't agree on the event's focus. Some wanted to emphasize learning for beginners, while others pushed for judging things based solely on innovation. Here's how I helped us find a middle ground..."

When using distant examples, quickly establish their relevance and then focus on showing the competency that the question has asked about. The context matters less than showing that you possess the skill in question.

Option 4: Honest Acknowledgment

Sometimes, ‘I have nothing’ is the best answer you can give:

"I don't have an example of that situation. In my roles so far, I've been fortunate to work with amazing managers where disagreements have remained professional."

This protects your credibility and shows curiosity about how they do things. It's far better than proffering an obviously made-up story or stumbling your way through a weak example.

Follow your acknowledgment by expressing a real interest in their experience. By doing this, you can turn the moment into a real conversation about how they handle similar situations. Interviewers respect that.

The Pyramid Method for Follow-Ups

When an interviewer asks follow-up questions, structure your response like a pyramid. Start with a direct answer (the peak), then expand downward through additional layers only if the interviewer wants more detail.

This mirrors the HSS pyramid from Chapter 3. There, you structured your initial story with a headline at the peak. Here, you're applying the same principle to follow-up questions: lead with your answer, then expand only as needed.

The Structure

Level 1 - Direct Answer: Give a clear, one-sentence response that directly addresses their question.

Check: "Would you like more detail on that?"

Level 2 - Brief Expansion: If they want more, provide three or four sentences with additional context.

Check: "Should I go deeper into the technical aspects?"

Level 3 - Full Detail: If they're still engaged, share complete technical details, implementation specifics, or broader context.

Example in Practice

Interviewer: "How did you handle rollback for this deployment?"

Level 1: "We used feature flags so we could disable the new code without redeploying."

Check: "Would you like more detail on our approach?"

Level 2 (if yes): "We wrapped all new functionality in feature flags that could be toggled without deployment. We also kept the old code paths active for two weeks. Our monitoring automatically disabled flags if error rates spiked above 2%."

Check: "Should I explain the technical implementation?"

Level 3 (if yes): "We used LaunchDarkly for flag management. Our monitoring system tracked error rates per feature, and we set up alerts to flag any spikes so the on-call engineer could disable the feature within minutes. We also built a dashboard showing flag status and error rates for each feature."

Why This Works

Employing the pyramid method respects the interviewer's time while also making sure they get the level of detail they’re after. It prevents the common mistake of overexplaining when a simple answer would suffice. It also helps you gauge their interest level and technical depth.

Most follow-up questions need only one or two levels. If an interviewer nods and moves on after your Level 1 answer, they got what they needed. If Level 2 satisfies their curiosity, stop there. Don't mechanically offer all three levels every time. An interviewer who leans back and says "Got it, thanks" is signaling they're ready to move on. An interviewer who leans forward and asks, "How did that actually work?" wants more depth. Match your responses to their engagement.

Starting with the conclusion feels unnatural at first, because we're trained to build up to our point. But interviewers appreciate getting the answer immediately, then being able to choose whether to dig deeper. This approach also helps when time runs short. That way, you've communicated the essential point even if there's no time for elaboration.

Use this method for any follow-up question, not just technical ones. Questions about team dynamics, project outcomes, or your decision-making process will all benefit from this structured approach.

Stop Reading Faces, Start Listening

One of the biggest interview mistakes is trying to read the interviewer's facial expressions. This misguided effort will often distract you from the conversation, and it will often lead to wrong conclusions.

Stop Reading Faces

Research consistently shows humans are terrible at accurately interpreting facial expressions, especially across cultures and in stressful situations. A serious expression might mean:

• They're deeply engaged in your story.
• They're thinking about follow-up questions.
• They're connecting your experience to their challenges.
• They’ve had a bad day.
• They want to hide their enthusiasm.
• That's just how their face looks when concentrating.

That smile might indicate:

• They appreciate your solution.
• They don’t want to discourage you after a poor answer.
• They're being polite.
• They're thinking about lunch.
• That's just their resting expression.

Trying to decode these signals wastes mental energy that would be better spent on the conversation. Worse, you might misinterpret neutral concentration as disapproval and start second-guessing yourself.

Cultural differences make face-reading even more unreliable. What might seem like disengagement in one culture could signal respect in another. Some interviewers maintain a poker face by design to avoid biasing candidates. If you try to interpret expressions, you're playing a guessing game you can't win.

What Actually Signals Engagement

Instead of reading faces, listen to their questions and responses. These provide real information:

Engagement signals:

• Asking follow-up questions.
• Connecting your story to their work: "We had a similar challenge..."
• Taking detailed notes.
• Asking for more specifics.
• Losing track of time because they're interested.

Potential disengagement signals:

• "Let's move to the next question," without any follow-ups.
• Rushing through their question list without probing.

Even these aren't perfect indicators. Some interviewers maintain consistent behavior regardless of their assessments. What seems like a generic response might not be a judgment on your answer, but just a reflection of their interview style. And if an interviewer keeps checking the time, they might simply be worried about fitting in all their required questions, not signaling disinterest in you. Your best strategy remains the same: tell clear, concise stories, and check in about the desired level of detail.

Focus on What You Can Control

You control your preparation, your delivery, and your energy. You don't control the interviewer's mood, their facial expressions, or their interviewing style. Focusing on what you can't control creates anxiety that will undermine your performance.

Your best move is always the same: use a check-in. Instead of guessing, ask if they want more depth. These check-ins will get you information you can use. They will also allow you to demonstrate professional communication skills that matter in real work environments.

Managing Energy Across Multiple Interviews

Back-to-back interviews will test your stamina. Your sixth interviewer deserves the same energy as your first. This requires active management.

Physical Energy: If you have multiple interviews, use the transition time between sessions wisely. Stand and stretch between sessions. Eat something small, like nuts or a bar, to keep your energy steady. If there's a break, use it to step away and reset for a minute.

Mental Energy: Reset your mind between interviews. Each interviewer is meeting you fresh, so don’t let your previous conversations cloud your thinking. Take 30 seconds to remind yourself what's interesting about this role. That helps you walk into the next session with fresh energy instead of carrying residue from the last one. Avoid the temptation to debrief the last interview in your head. Stay present for what's next.

Story Variety and Freshness: Using different stories with different interviewers keeps your delivery energetic, and it serves another practical purpose. Most companies hold panel meetings after all interviews, where the interviewers share what they heard from you. Telling every interviewer the same story gives the hiring panel a narrow picture of what you can do. Aim to showcase different experiences and competencies across your interview day. If you must repeat a story, find a new angle or emphasis. For example, the second telling of your migration story might focus on stakeholder management instead of technical details. Variety keeps you engaged and gives the hiring panel a broader view of what you can do.

Managing Difficult Moments: If one interview goes poorly, don't let it contaminate the ones that follow. Let it go. One bad round doesn't sink you; plenty of people get offers despite bombing one interview. Each interviewer is forming their own assessment, so give the next one your full effort. A difficult moment with one person doesn't determine your outcome. Give the next interviewer your best effort.

After the Interview

The interview day is over, but you're not done. What you capture now will make your next interview better.

Learning From Each Interview

Immediately after the interview day ends, while the details are still fresh in your mind, capture your observations. Don't wait until the next day or until you hear back from the company. Memories fade quickly, and specific details are the best for improvement.

Questions you weren't prepared for: Write these down verbatim. Prepare stories for next time or practice your framework for handling unexpected questions. If you weren’t able to answer well in the moment, develop a strong response now so you're ready if it comes up again.

Stories that landed well: Note which examples resonated and why. Did the interviewer connect with the technical challenge? The team dynamics? The business impact? Understanding what worked helps you select stories strategically for future interviews.

Moments of confusion: Where did communication break down? Did you use unclear terminology? Skip important context? Assume too much knowledge? Use those moments to teach you where to improve clarity. Be specific about what went wrong and how you'll prevent it from occurring in a future interview.

Follow-ups that revealed gaps: What did interviewers probe that you couldn't answer well? These questions show what matters for the role and where to deepen your preparation. If multiple interviewers from the same company asked about the same capability, that was a clear signal about their priorities.

Don't dwell on mistakes or replay the interview endlessly in your head. Focus on extracting patterns that you can use to improve your interviewing skills. For example, if multiple interviewers across different companies have pressed you on how you handle ambiguity in technical decisions, that's a gap in your story bank worth addressing.

Building Interview Stamina

Your first interview will feel exhausting. That's normal. Each one after that gets easier as you learn what works for you.

Each interview teaches you something about performing under pressure. You learn which preparation techniques are most helpful to you. You discover which stories work best. You get comfortable with the uncertainty and can adapt more quickly to different interviewer styles.

As you sit through more interviews, focus on maintaining your authenticity rather than perfecting a performance. Before each interview, remember why your work mattered. Not just the metrics, but the real impact. That performance optimization didn't just improve numbers; it made the app usable for people with older phones.

When you talk about work you're proud of, don't hold back. That energy is contagious, and it makes the interview better for everyone. You're not trying to be a polished performer; you're trying to be yourself, at your best.

The Path to Natural Delivery

Nailing behavioral interviews requires you to balance structure with flexibility. You need your HSS framework as a foundation, but you must build genuine conversations on top of it.

Your stories are vehicles for describing your experience. The best delivery feels like sharing stories with an interested colleague, not presenting to an evaluation committee. When your delivery feels like a real conversation but still hits the key points, you're giving your interviewers exactly what they need to fight for you in the debrief.

The investment in mastering your delivery will pay off immediately. Each interview gets easier. Your confidence grows. Your stories become more natural. You start enjoying the opportunity to discuss your work with people who understand it. This positive energy becomes part of what makes you a really great hire.

Trust the process. You've done interesting work, and you've prepared strong stories. Now show up rested, present, and ready to share what you've accomplished. When you nail the delivery, your experiences will speak for themselves.